<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Identify a Device</title><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"><meta name="keywords" content="Intellon, Atheros, Qualcomm, HomePlug, powerline, communications, INT6000, INT6300, INT6400, AR7400, AR7420"><link rel="home" href="index.html" title="Qualcomm Atheros Open Powerline Toolkit"><link rel="up" href="ch05.html" title="Chapter 5.  Procedures"><link rel="prev" href="ch05s03.html" title="Select an Interface on Windows"><link rel="next" href="ch05s05.html" title="Browse the Network"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">
			Identify a Device 
			</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch05s03.html">Prev</a> </td><th width="60%" align="center">Chapter 5. 
		Procedures 
		</th><td width="20%" align="right"> <a accesskey="n" href="ch05s05.html">Next</a></td></tr></table><hr></div><div class="section" title="Identify a Device"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="procedure-identify-device"></a>
			Identify a Device 
			</h2></div></div></div><p>
			Before you start working with Atheros powerline devices, you should determine the chipset and firmware revision because that will determine the types of operations that can be performed and the order in which some operations should be performed. The following example illustrates how to determine this information.  
			</p><div class="example"><a name="script-example-device-identification"></a><p class="title"><b>Example 5.6. 
				Device Identification
				</b></p><div class="example-contents"><pre class="screen">
# int6k -r
eth1 00:B0:52:00:00:01 Fetch Version Information
eth1 00:B0:52:DA:DA:23 INT6300A0 INT6000-MAC-3-0-3001-1081-LA-A NOT_UPGRADEABLE
eth1 00:B0:52:FE:87:2D INT6000A1 INT6000-SL-0-1-0110-200-2006-0415-BETA NOT_UPGRADEABLE
</pre></div></div><br class="example-break"><p>
			This example  demonstrates several things. 
			</p><p>
			First, the <a class="ulink" href="int6k.7.html" target="_top">int6k</a> <strong class="userinput"><code>-r</code></strong> option requests hardware and software revision information from a device by sending an Atheros <code class="constant">VS_SW_VER</code> vendor-specific managerment message and waiting for a response. Atheros vendor-specific management messages are described in the <em class="citetitle">Atheros HomePlug AV Firmware Technical Reference Manual</em>. It you do not have access to this document then many toolkit features may be difficult to understand.
			</p><p>
			Since we did not specify an Ethernet interface on the command line, the default interface was used. In this case, the default interface was <code class="varname">eth1</code> and so we observe that <code class="varname">eth1</code> was used to both send requests and receive responses.
			</p><p>
			Since we did not specify a device address on the command line, the default address was used. Device addresses are also known as <acronym class="acronym">MAC</acronym>, <span class="quote">“<span class="quote">Ethernet</span>”</span> or <span class="quote">“<span class="quote">hardware</span>”</span> addresses. They uniquely identify a device on a network. Unlike Ethernet cards,  powlerlines device do not have IP addresses. 
			</p><p>
			The default device address for toolkit programs is <code class="constant">00:B0:52:00:00:01</code>. This address is the Local Management Address (<acronym class="acronym">LMA</acronym>). All Atheros devices connected to the local host will respond to this address and include their actual address in the response. In the above example, two devices responded. This means that both were connected directly to <code class="varname">eth1</code>, perhaps via a network hub. Observer that device <code class="constant">00:B0:52:DA:DA:23</code> is an INT6300 and device <code class="constant">00:B0:52:FE:87:2D</code> is an INT6000. The first device is running Atheros firmware and the second device is running the Atheros Softloader. 
			</p><div class="example"><a name="script-example-device-configuration"></a><p class="title"><b>Example 5.7. 
				Inspecting Device Configuration
				</b></p><div class="example-contents"><p>
				To find out more about device <code class="constant">00:B0:52:DA:DA:23</code> we might issue the following command where option <strong class="userinput"><code>-I</code></strong> requests identity information stored in the device <acronym class="acronym">PIB</acronym>. In this case, we specified the device by <acronym class="acronym">MAC</acronym> address to prevent other local devices from responding. There is no harm in having both devices respond so we could have specified both hardware addresses.
 				</p><pre class="screen">
# int6k -I 00:B0:52:DA:DA:23
eth1 00:B0:52:DA:DA:23 Device Identity
eth1 00:B0:52:DA:DA:23 -------
        PIB 3-2 7864 bytes
        MAC 00:B0:52:DA:DA:23
        DAK 24:03:D7:84:09:A0:9A:78:8D:F6:82:75:AF:0D:0F:D8
        NMK 50:D3:E4:93:3F:85:5B:70:40:78:4D:F8:15:AA:8D:B7 (HomePlugAV)
        NID B0:F2:E6:95:66:6B:03
        NET Jupiter-23
        MFG Intergalactic Death Rays Inc.
        USR Rattin Tordo
        CCo Auto
</pre><p>
				Pay special attention to the <acronym class="acronym">MAC</acronym> address after flashing <acronym class="acronym">NVRAM</acronym>. Hardware address <code class="constant">00:B0:52:00:00:03</code> indicates the Default <acronym class="acronym">PIB</acronym> used when no other <acronym class="acronym">PIB</acronym> is available. The Default <acronym class="acronym">PIB</acronym> disables communication over powerline.
				</p><p>
				Pay special attention to the <acronym class="acronym">NMK</acronym> when devices cannot communicate. Devices having different <acronym class="acronym">NMK</acronym> values will not form a network. Conversely, all devices having the same <acronym class="acronym">NMK</acronym> will form a network. This becomes important when programming large numbers of devices. You must have an out-of-the-box networking strategy that balances user convenience and network security.
				</p><p>
				The string next to the <acronym class="acronym">NMK</acronym> indicates that password <span class="quote">“<span class="quote">HomePlugAV</span>”</span> was used to generate that key. This is one of two default passwords and keys used by Atheros. In some cases, it may be another clue that the device is using the default <acronym class="acronym">PIB</acronym>.
				</p></div></div><br class="example-break"></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch05s03.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch05.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch05s05.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">
			Select an Interface on Windows
			 </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 
			Browse the Network
			</td></tr></table></div></body></html>
